Method and apparatus to validate a subscriber line

ABSTRACT

A method is described to verify the identity of a user. The method, in one example embodiment, comprises obtaining automatic number identification (ANI) data or billing telephone number (BTN) data associated with a subscriber line of a telecommunications network; obtaining identification data associated with a subscriber, said identification data being different from the ANI data or the BTN data; searching a first database using the ANI data or the BTN data to determine first reference subscriber data; searching a second database using the identification data to determine second reference subscriber data; comparing the first reference subscriber data to the second reference subscriber data; and verifying an identity of the subscriber based on the comparing.

The present application is a continuation of U.S. Pat. No. 7,054,430entitled “METHOD AND APPARATUS TO VALIDATE A SUBSCRIBER LINE” filed Aug.20, 2002 which claims the benefit of the filing date of U.S. provisionalpatent application No. 60/314,604 entitled “METHOD OF VALIDATING ASUBSCRIBER LINE” filed Aug. 23, 2001. U.S. Pat. No. 7,054,430 and U.S.provisional patent application No. 60/314,604 are incorporated herein byreference in their entirety.

BACKGROUND TO THE INVENTION

An increasing number of vendors are offering goods and/or services whichmay be purchased via a communication network such as a telecommunicationnetwork. For example, the customer may conduct a transaction via asubscriber line using a landline telephone or a personal computer.Conventionally, credit or debit card details are furnished by thecustomer to the vendor to effect payment for the goods and/or services.As many customers are hesitant to supply credit or debit card detailsover a communication network, an alternate method of payment would beadvantageous. However, if an alternate method is used, verification ofthe payment method should preferably take place prior to concluding thetransaction.

BRIEF DESCRIPTION OF THE DRAWINGS

The invention is now described, by way of example, with reference to theaccompanying diagrammatic drawings.

FIG. 1 shows a schematic block diagram of a subscriber line validationsystem, in accordance with the invention, for validating a subscriberline of a communication network;

FIGS. 2 to 4 show a schematic flow chart of a method, in accordance withthe invention, for validating the subscriber line;

FIG. 5 shows a schematic block diagram of how the system may be used ina conventional commercial environment; and

FIG. 6 shows a schematic representation of a sample telephone billplatform which the system can automatically update.

FIG. 7 shows a diagrammatic representation of machine in the exemplaryform of a computer system within which a set of instructions, forcausing the machine to perform any one of the methodologies discussedherein, may be executed.

DETAILED DESCRIPTION

Referring to the drawings, reference number 10 generally indicates anexemplary subscriber line validation system, in accordance with anaspect of the invention, for validating a subscriber line 17 of asubscriber. In one exemplary embodiment, the subscriber line 17 is atelephone line or the like which a consumer or business 11 (see FIGS. 1and 5) obtains from a telephone company (Telco) 13 or a local exchangecarrier (LEC). As described in more detail below, the system 10 usesline data in the exemplary form of an automatic number identification(ANI) service to obtain the telephone line number of the subscriber line17 thereby to validate the subscriber line 17 when the subscriber line17 initiates a communication or connection. In one exemplary embodiment,the line number obtained from the ANI service is used to investigatevarious databases to obtain, for example, an indication of the creditworthiness of the subscriber account associated with the subscriber line17. It is to be appreciated that any electronic apparatus, e.g. apersonal computer, PDA, cellular telephone, or the like may be used toinitiate the communication.

Referring in particular to FIG. 1 of the drawings, the system 10includes an application program interface (API) 14 which is connected toa vendor 12 or service provider (see also FIG. 5) of goods and/orservices which requires validation of a subscriber account. The vendor12, which could for example be an Internet Service Provider, may requestthe validation of the subscriber line 17 prior to concluding anelectronic transaction with a subscriber (e.g., a consumer or business11) via the subscriber line 17. It is, however, to be appreciated thatthe API 14 may be connected to a variety of different hosts or clientswhich require validation of a subscriber line via which the vendor maycarry out transactions for goods and/or services.

In one exemplary embodiment, the system 10 is connected to a pluralityof vendors which conduct transactions with users via line terminationequipment such as a telephone, a personal computer or the like. Suchvendors, when conducting transactions, may preferably charge a user fortheir services by adding such charges to a telephone account of the userrather than charging the goods and/or services to a credit card, debitcard, or the like. Accordingly, the validation of the subscriber line17, and the subscriber account associated with the subscriber line 17,may be of benefit to the vendor 12 prior to completing a transaction.The validation may include determining whether or not the subscriberline 17, via which the communication is made to the vendor, is abillable line and, accordingly, the subscriber account associated withthe subscriber line 17 may thus be billed for the transaction.

In one exemplary embodiment, the vendor 12 communicates a request to thesystem 10 and forwards the subscriber line number, determined by the ANIservice, to the system 10 via its API 14. The system 10 then processesthe information received from the vendor 12 and provides a validationstatus, e.g. a code indicating a valid billable number or a codeindicating that the subscriber line number is not a valid billablenumber (e.g. unbillable or non-billable). In particular, a plurality ofcodes associated with various statuses of the subscriber line 17 may becommunicated to the vendor 12 as described in more detail below.

The system 10 includes hardware and software to implement the invention.In the exemplary embodiment, the system 10 includes a comparator module18, a threshold database 20, an OFFNET database 22, an ONNET database24, a competitive local exchange carrier (CLEC) database 26, a 42 BLOCKdatabase 28, a block and cancel database 30, an unbilled and/or unpaidbills database 32, line identification database (LIDB) short term cache34, a validity check module 36, a regional account office (RAO) database38, an operating company number (OCN) database 40, an ONNET database 42,an address verification database 44, a customer account record exchange(CARE) results database 46, an ANI watch database 48, and an NPA(Numbering Plan Area) exchange database 50. It is to be appreciatedthat, in less sophisticated embodiments of the invention, all of theabove databases need not be included. However, for enhanced accuracy,all of the above databases are preferably included. Further databasesmay also be included to further enhance the reliability of thevalidation process.

In addition to any one or more of the above databases, the system 10 isin communication via a conventional communication channel with anoff-site or, in some embodiments, on-site line identification database(LIDB) host 52. The LIDB host 52 may include a line number portability(LNP) database. In one exemplary embodiment, the LNP database may frontend access to a plurality of industry standard LIDBs (e.g. 13 differentLIDBs). The LNP database may however be a separate database. Asdescribed in more detail below, the system 10 communicates thesubscriber line number to the LIDB host 52 which, in turn, communicatesreference subscriber data in the form of industry standard LIDB codesback to the system 10 for processing. The system 10 then processes theLIDB codes to provide the vendor with validation data relating to thesubscriber line 17. Unlike conventional LIDB applications which use LIDBto make decisions regarding destination subscriber lines or callcompletion decisions, e.g. decisions for calling cards, collect andthird party toll services or the like, the system 10 may be used toidentify telephone numbers being served by CLECs in order to ensure thatcalls are routed correctly on ported lines.

Broadly, the system 10 has a variety of different components, includinga communication module defined by the API 14, and a processor module 54.The a processor module 54 includes the various databases 20 to 32 aswell as the comparator module 18 and the validity check module 36, andan interrogation module 56 for interrogating the LIDB host 52. It is tobe appreciated that the aforementioned modules may be defined by one ormore servers with associated databases. Further, in the drawings, theLIDB host 52 is shown as a single database but may comprise manydifferent LIDB databases maintained by various LECs and, accordingly,may be located at various different geographic locations.

Referring in particular to FIGS. 2 to 4 of the drawings, a flow chartdescribing the method of operation of the system 10 is shown. In oneexemplary embodiment, a vendor 12 initiates a request to the system 10to validate a subscriber line 17 via which the vendor 12 wishes totransact with a customer (consumer or business 11). As shown atoperation 60, the system 10 first checks to see if the subscriber linenumber is present in the request from the vendor 12 and, if no linenumber is present, a return code 121 is generated and communicated tothe vendor as shown at operation 62. The code 121 indicates to thevendor that the system 10 is unable to process the request. If, however,the subscriber line number is present in the request from the vendor 12,the system 10 then checks if the subscriber line number captured(hereinafter also referred to as the ANI) and a billing telephone number(BTN) match, as shown at operation 64 (see also the comparator module 18in FIG. 1). In one exemplary embodiment, the BTN may be sourced from theconsumer or customer 11 when a transaction is requested by the customer11. If, however, the ANI and the BTN do not match, then the processormodule 54 generates a code 120 (see operation 66) to indicate that thecaller and the owner of the line number are not the same person (e.g.subscriber inputs a BTN and calls from a different ANI) and the relevantmodified code is then returned to the vendor 12. If the ANI and the BTNdo match, the processor module 54 interrogates the threshold database 20(see operation 68) to ascertain whether or not the line number hasreached its threshold (e.g., a predefined client threshold parametersuch as an account threshold indicating a maximum dollar amount that maybe charged to the account). If the line number has reached itsthreshold, the processor module 54 then generates a code 60, as shown atoperation 70, which is then communicated to the vendor 12 to indicatethat the line number should not be granted service. In other words, thesubscriber account cannot be billed for the goods or services requestedby the customer 11 from the vendor 12.

If the threshold for the particular subscriber line 17 has not beenreached, the system 10 may then interrogate its OFFNET database (seeoperation 71) to check if the industry standard NPA/NXX and operatingcompany number (OCN) of the subscriber line 17 is present in the OFFNETdatabase 22. The OFFNET database 22 includes NPA INXX and OCNcombinations of operating companies with which the proprietor or user ofthe system 10 does not have billing and collection agreements to billinto the telephone company's or Telco's bill page associated with thesubscriber line 17. Accordingly, the proprietor or user of the system 10is unable to include a charge in the account associated with thesubscriber line 17 on behalf of the vendor 12 for the transactioncarried out with the vendor 12 via the subscriber line 17.

If the line number is in the OFFNET database 22, then the processormodule 54 generates codes 130 to 133 (see operation 72) and communicatesthese codes to the vendor 12. The codes 130 to 133 indicate that theNPA/NXX and OCN for the particular line number 17 are not billable and,accordingly, charges for goods and/or services requested by a customer11 via the subscriber line 17 cannot be included in a monthly account orthe like by the system 10. As shown in Table 2 below, the codes 130 to133 provide an indication to the vendor 12 why the subscriber line 17 isnot billable or deliverable. If the subscriber line number is notincluded in the OFFNET database 22, a check is conducted to see whetheror not the subscriber line number is included in the ONNET database 24.This check is however optional in the embodiment depicted in thedrawings, but in certain embodiments, may be mandatory if the system 10does not include the OFFNET database 22.

Thereafter, as shown in operation 78, the processor module 54 checks tosee if the line number 17 is found in a known CLEC table in the CLECdatabase 26. CLEC numbers are those line numbers that are known to haveported to a CLEC and, accordingly, the proprietor of the system 10 isthus unable to route these line numbers to the correct billing entities.If the line number is found in the CLEC database 26, then the processormodule 54 generates a code 140 (see operation 76), which is communicatedto the vendor 12. The code 140 indicates that the line number is notbillable for the CLEC and the system 10 can thus not charge thetransaction to the subscriber account associated with the subscriberline 17.

If the line number is not found in the CLEC database 26, then the system10 may check to see if the subscriber of the line number has requested a4250 billing block as shown at operation 78. In particular, theprocessor module 54 interrogates the 42 BLOCK database 28 and, if thenumber is located in the database 28, which indicates that monthlyrecurring charges (4250 charges) are prevented from being billed to thatline number, the processor module 54 generates a code 150 (see operation80) which is communicated to the vendor 12 to indicate that billing tothe particular subscriber line 17 has been blocked.

If, however, the subscriber line 17 has not been blocked, the system 10may then check at operation 82 if the line number is located in theblock and cancel database 30 and, if so, the processor module 54generates codes 160 and 161 which are then communicated to the vendor 12as shown at operation 84. The block and cancel database 30 includesrequests from owners of subscriber lines, agencies, businesses, or thelike that a service be canceled or blocked from further billing.Thereafter, the system 10 may interrogate the unbilled and/or unpaidbills database 32, as shown at operation 86, to check if there is ahistory of any unpaid bills and/or unbillable bills associated with thesubscriber line 17. Unbillable bills relate to those subscriber linenumbers where previous attempts have been made to bill charges to thesubscriber account associated with the subscriber line number 17, andwhich have been returned as unbillable. If the processor module 54locates the subscriber line number in the unbillable and/or unpaid billsdatabase 32 then, as shown at operation 88, a code 170 is generated andcommunicated to the vendor 12 to indicate that the subscriber linenumber was previously found to be unbillable and is still considered tobe unbillable.

The processing described in the abovementioned operations may conduct apreliminary investigation into the subscriber line number or ANI toprovide an initial indication of whether or not the ANI corresponds witha billable subscriber line. Once the initial investigation has beenconducted in certain embodiments, the system 10 then uses the ANI toobtain reference subscriber line data in the form of LIDB codes from oneor more industry standard databases, e.g. the LIDB host or database 52.Examples of the LIDB codes used in the system 10 are shown in Table 3below.

As shown at operation 90, if the ANI is not found in the LIDB database52, then the system 10 cannot provide any validation data to the vendor12 on this subscriber line and an appropriate code is then communicatedto the vendor as shown at block 92.

Once the LIDB database or host 52 has been interrogated, it returnsindustry standard LIDB codes and line number portability (LNP) data tothe system 10 as shown in operation 94. The LIDB codes may then bemapped or translated by the processor module 54 into modified validationcodes (see Table 3) which provide relevant validation information to thevendor 12. As can be seen from Table 3, the same modified validationcode can be generated from a plurality of different LIDB codes. Once theLIDB information codes have been returned to the processor module 54,the LIDB codes, including an OCN and RAO response codes, are fed intothe validity check module 36 as shown at operation 96.

As mentioned above, the LIDB host 52 may also provide LNP data to thesystem 10. The LNP data is used to identify subscriber line numbers thathave ported to a CLEC. If a subscriber line has been ported to a CLEC,the billing ONNET status of the CLEC may be verified in the CLECdatabase 26. The LNP identifies the facilities based CLECs which areCLECs that have been assigned all the line numbers for an NPA/NXX in aspecific geographic territory. This type of CLEC may be in control ofthe cable, dial tone and billing envelope for that number. In oneexemplary embodiment, the LNP cannot be used to identify CLEC sellers,which have resold the subscriber line under their brand, but still leasethe cable and tone from an incumbent local exchange carrier (ILEC).Accordingly, a third-party billing facility, e.g. a proprietor or userof the system 10, may be unable to process transaction data onto a billpage of the CLEC reseller bill page. In order to identify resellerCLECs, the system 10 may compare RAO and OCN information, returned fromthe LIDB host 52, to data in the ONNET database 24. The OCN is the localTelco that owns the subscriber line number and the RAO is the office ofthe Telco that is responsible from a billing standpoint for thesubscriber line number.

If the validity check module 36 determines that the response codes areinvalid, the system 10 generates modified codes 180 to 999 (seeoperation 98 and Table 2) which are communicated to the requestor orvendor to indicate that the mapping of the LIDB codes to the modifiedcodes concluded that the line is an unbillable subscriber line.

If the validity check module 36 confirms the validity of the LIDB codesand, in the event of the line number being a billable line number, theprocessor module 54 then may check the RAO database 38 to ascertainwhether or not the RAO is billable, as shown at operation 100. If theRAO is not billable, then the processor module 54 generates andcommunicates a return code 143 (see operation 102) to indicate to thevendor 12 that the line number belongs to a CLEC which is not billableby the system 10.

In a similar fashion, at operation 104 the processor module 54 checks tosee if the OCN returned from the LIDB host 52 corresponds with a knownCLEC or if the OCN corresponds with an OFFNET OCN and is therefore alsounbillable by the system 10. If the line number corresponds to an OCNthat is not billable, a return code 142 is generated by the processormodule 54 and communicated to the vendor (see operation 106).

If the subscriber line number has passed the RAO and OCN checks and,accordingly, it appears that the number is billable, the processormodule 54 may then check to see if a new NPA /NXX and OCN combinationfor this line number is guidable to the correct local Telco for billing(see operation 108). If the line number is not guidable, then the system10 generates a code 141 at operation 110 which is communicated to thevendor to indicate that, even though the line number is billable, theproprietor of the system 10 is unable to guide the billing informationto the new Telco for billing. Accordingly, the telephone number is infact non-billable insofar as the system 10 is concerned and a declinestatus is therefore communicated to the vendor 12.

The abovementioned operations are carried out to ascertain whether ornot the subscriber line can be billed for the goods and/or servicesrequested. However, to enhance the accuracy or reliability of the system10, further checks or verification may be conducted as described below.

In the event that the subscriber line number has passed or complied withthe abovementioned checks, and has thus not yet been rejected, thesystem 10 may perform address verification procedures at operation 112.In particular, when the ANI is communicated to the API 14, location datais also provided which has been fed in by the user, e.g. via a computerterminal, orally over a telephone, or the like. The system 10 theninterrogates an address verification database 44 to compare the addressor location data (e.g. a ZIP code) supplied by the customer 11 with areference address data as shown at operation 112. If, however, theaddress supplied by the customer 11 does not match with the address inthe verification database 44 or, the addresses are not within apredefined range or area, the processor module 54, as shown at operation114, generates codes 10 to 39 which are then communicated to the vendor12 to indicate the level of likelihood that the caller (ANI) and theaccount owner are the same person.

During the address verification operation 112, the system 10 mayinterrogate a customer account record exchange (CARE) database 46 (whichcan be an on-site database which is regularly updated), to provideenhanced reliability. In particular, in one exemplary embodiment, theCARE database 46 or information site is one or more industry standardoff-site databases which allow consumers to select or change their longdistance service provider. Local Telcos forward specific customerinformation to the LEC associated with the subscriber. In one exemplaryembodiment, the information communicated includes a new telephonenumber, a billing address, an installation date, a person ororganization responsible for the account, or the like.

As shown at operation 116, the system 10 may interrogate the CAREdatabase or information site and CARE data is then loaded into CLEC andnew line databases to perform certain fraud and/or billing checks. TheCARE information investigation may occur after a successful validationevent. In one embodiment, once the system 10 has validated thesubscriber line 17, the subscriber line number data is sent to a CAREdatabase provider hosting the CARE database 46 to obtain the BNA(Billing Name and Address) and age of the account. In one exemplaryembodiment, the information is returned within 48 hours and thenprocessed. CARE records that are returned without BNA and NO ACCOUNTcodes may be inserted into the CLEC database 26 for future reference.Accordingly, if the BTN is presented again at a later date, it will failthe CLEC check operation 74 (see FIG. 2).

The ANI watch database 48, which may include historical and adjustedinformation, may be used by the system 10 to determine if the accounthas previously been adjusted (see operation 116). In one exemplaryembodiment, this operation includes ascertaining previous requests bythe subscriber for credit, obtaining data on any written off amounts forcharges that were billed to a bill page, or the like.

If adjustments have previously been made to the account associated withthe subscriber line 17, the processor module 54 generates codes 1 to 5(see operation 118) to indicate to the vendor 12 that the adjustmentshave previously been made. If no adjustments have been made, theprocessor module 54 checks to see whether or not the subscriber linenumber has a business line indicator as shown at operation 120. If thebusiness line indicator is active, the system 10 generates a code 70(see operation 122), which is communicated to the vendor 12 to advisethat the line is a business line. Thereafter, as shown in operation 124,the processor module 54 may check to see if the subscriber line numberhas been in service for less than about 90 days and, if so, a returncode 80 (see operation 126) is generated to advise the vendor 12 who maythen selectively decide whether or not to conclude the transaction. Adatabase of new numbers may be updated with the new number.

Thereafter, the system 10 may interrogate the ANI watch database 48 (seeoperation 128) to ascertain whether or not the area code of the linenumber has been changed or is scheduled to change. In one embodiment,this interrogation is for billing purposes only and is not used todecide upon the validity of the request. In this operation, the vendor12 requesting the validation updates the billing file with the new areacode number, and the processor module 54 generates a code 110 (seeoperation 130) to advise the vendor 12 of the scheduled change to thearea code.

Once the line number has passed all the aforementioned checks, thesystem 10 may conclude that the subscriber line 17 is in fact a billablesubscriber line based on the data obtained using ANI techniques and,accordingly, the transaction may be charged directly to the account ofthe subscriber. Accordingly, the system 10 then generates a code 000(see operation 134) which is communicated to the vendor 12. The code 000may define an approved status following both a billable line numberinquiry as well as several fraud checks which are carried out by thefraud control module 132 (see FIG. 1). If the subscriber line number ofthe subscriber line 17 has passed the abovementioned checks and a returncode 000 is generated, the procedure shown in FIG. 4 is carried outwhereafter the process terminates at operation 136. Thus, operation 136may define the end of the process during which the various checks havebeen conducted on the subscriber line 17 to assess whether or not it isa billable subscriber line that charges may be billed to. Operation 138defines, in one embodiment, the last operation to which the processjumps when, at any point during the abovementioned process, the linenumber is found not to be billable (or a creditworthiness decision isrequested) and the inquiry is accordingly terminated and the relevantcode is communicated to the vendor 12.

In one exemplary embodiment, the abovementioned operations are executedin real-time. However, information sources that do not allow checks onthe line number in real time may be carried out subsequently on thesubscriber line number. In one embodiment, once the real-time evaluationis carried out and the return code 000 is communicated to the vendor 12,and should the vendor 12 decide to proceed with the transaction,transaction data is then returned to the system 10 by the vendor 12 fora pre-billing validation check or actual billing. During the actualbilling, the system 10 may access an account folder of the subscriberline at the Telco and insert the charges due to the vendor 12 for itsgoods or services. As shown at operation 140, subscriber line numbersmay be sent to the CARE database 46 to determine if the BNA is availableat the local Telco. If the folder is not available, the local Telcosends the BNA and codes as to why the number is unavailable. If the BNAis found in the CARE database 46, the processor module 54 may then checkto see whether or not the account was created within the last 90 days asshown at operation 142. If the account was not created within the last90 days, then the business indicator is checked as shown at operation144 and the process ends as previously shown at operation 146. If,however, the number was found in the CARE database 46, the account wascreated within the last 90 days, or has an active business indicator,then the system 10 may generate the appropriate codes, which arecommunicated to vendor 12, and the process terminates as shown atoperation 148.

The above process has been described in terms of modified codes set outin Table 2 but, it is to be appreciated, that any other defined set ofcorresponding codes may be provided so long as the codes are mappedonto, or generated in response to, any one or more of the industrystandard LIDB codes.

A summary of the codes generated by one exemplary embodiment of thesystem 10 during execution of the validation process is provided inTable 1 below. TABLE 1 Modified codes generated during the BTNValidation Process. Code Generated and ref to flow charts Description ofcode Return Code 121 Indicates inability to proceed with validation;returned to requestor See operation 64 Checks if ANI captured and BTNprovided match (not required in all scenarios) Return Code 120 Indicatescaller and # (line number) owner are not the same person; returned torequestor See operation 68 A defined Threshold limits the number ofattempts on that # within a certain timeframe Return Code 60 Indicates #may not be granted service; returned to requestor. See operation 71Checks the NPA/NXX and OCN to those in the OFFNET. OFFNET = NPA/NXX andOCN combinations where proprietor of the system 10 does not have aBilling and Collections agreement to bill into the Telco's' bill page.Return Code 130-133 Indicates that NPA/NXX & OCN for that Number are notbillable; returned to requestor See operation 74 Checks the line numberto see if found in known CLEC table. These are numbers that are known tohave ported to a CLEC. Proprietor is unable to route these # to thecorrect billing entities. Return code 140 Indicates # not billable forCLEC; returned to requestor. See operation 78 Checks line # to see ifowner has requested a 4250 Billing block. This block prevents monthlyrecurring (4250) charges from being billed to that line #. Return Code150 Indicates that billing to a particular subscriber line has beenblocked; returned to requestor. See operation 82 Checks line number forinclusion in the Block and Cancel database. This database includesrequests from line # owners, agencies, businesses etc that haverequested that service be cancelled and or blocked from further billing.Return Code 160-161 Indicates number found in Block and Cancel and isnot billable; returned to requestor. See operation 86 Checks line # forunbillable history. Unbillables are #s where tried to bill chargespreviously and have been returned as unbillable. Return Code 170Indicates # has unbilled before and is still considered unbillable;returned to requestor. See operation 90 If # not found in Unbillable,then routed to LIDB for info. ITEM Description See operation Identifiesinfo returned from LIDB re. that line #; Response 94 Code = status aboutthat # as a call termination point. OCN = Operating Company # = thelocal Telco that owns that #. RAO = Regional Accounting Office = theoffice of the Telco that is responsible from a $ flow standpoint forthat #. See operation Checks the validity of the LIDB code returned forthe number as a 96 Billable #. This is where the mapping of the LIDBcodes to the proprietor validation codes happens. Return Code Indicatesthe mappings of the LIDB codes to the proprietor Val reply 180-999codes. Each of these indicate a non-billable #; returned to requestor.See operation Checks if RAO returned is an RAO that is not billable. 100Return Code Indicates that the # belongs to a CLEC and is unbillable;returned to 143 requestor. See operation Checks if OCN returned fromLIDB is a known CLEC or OFFNET 104 OCN and therefore unbillable. Returncode 142 Indicates that the new OCN is not billable; returned torequestor. See operation 108 Checks to see if new NPA/NXX & OCNcombination for # is guidable to the correct local Telco for billing.Return code Indicates that even though the # is billable, the system isunable to 141 guide to the new Telco for billing; unguidable =unbillable; # returned to requestor. The operations to indicate if # isbillable have been completed. The next operations provide additionalinformation about the # for the requestor e.g. to decide if and how muchcredit to extend for services. They also provide additional billinginformation. See operation Provides address verification (if required).Matches # to address to 112 determine likelihood of person dialing tothe person that owns the account at local Telco. Return Code Indicatesthe level likelihood that the caller (ANI) and acct owner are 10-39 thesame. Returned to requestor. See operation Checks to see if # has hadadjustment activity previously. This 116 includes request for credit,written off for charges that billed to a bill page. Requestor makescredit decision based on #s history of credits, adjustments, write offs.Return Code 1-5 Indicates the type and source of adjustment to chargesto that #. Returned to requestor. See operation Checks to see if the #has a business line indicator. Requestor 120 decides if would like toextend service or not. Return Code 70 Indicates that the # is identifiedas a business. See operation Checks to see if the # has been in serviceless than 90 days. 124 Requestor makes a decision about how much serviceto offer # without much payment history. Return Code 80 Indicates thatthe # has been in service less than 90 days. See operation Checks if theArea Code of the # has been scheduled to change. This 128 is for billinginformation purposes only. Requestor updates billing filed with newnumber. Return Code Indicates Area Code has been scheduled to change.New number is 110 appended to end of record. See operation If the numberpasses all the previous checks, then 000 code is 134 returned torequestor. The Validation is complete for this request. See operationEnd of validation for numbers that did not pass or were found in 138other checks. END OF REAL TIME VALIDATION EVENT Information sources thatdo not allow checks on the # in Real-time (r-t), happen on # that wasreturned as 000 after the r-t validation event has completed. The #s areloaded into the appropriate databases. This information will be providedonce the # is returned for billing. Operations 140, 142, Indicates pathfor those #s returned with a 000 144 code. See operation 140 #s are sentto CARE source to determine if BNA (billing Name and Address) availableat local Telco. Telco sends BNA and codes as to why unavailable. CLEC #sthat are returned with codes that indicate the # has moved to a CLECfrom the local Telco are loaded into the CLEC table. See operation 142#s are sent to the CARE source to determine if the account has beencrested within the last 90 days. The response codes indicate thiscondition. New within 90 #s that are returned with codes that indicatethis condition are loaded into the NEW table. See operation 144 #s aresent to a Business source. This source identifies which numbers belongto businesses. Biz table Numbers that are indicated as being line #sthat belong to businesses are loaded in this table.

Table 2 (see below) provides the various actions, which are executed inresponse to a modified validity code. The table provides an exemplarydescription and explanation of each code. Return codes 001 to 179 relateto failure codes, which are generated by the system 10 prior toinvestigation of the LIDB host 52. Return codes 180 to 451 are generatedduring the LIDB code checks. In the event of the subscriber line 17failing the checks carried out on it, the system 10 provides optionaluse of a credit card and, accordingly, Table 2 sets out codes which thesystem 10 generates in response to executing a standard credit cardenquiry for a particular transaction. If the system 10, which may bedefined by a server and associated databases, is down, codes 994 to 999are generated and communicated to the vendor. TABLE 2 Validation & BNAReply Codes Code Action DESCRIPTION EXPLANATION BILLABLE CODES 000Approved Billable; was not found during Passed all billing and fraudcontrol fraud control checks checks FRAUD CONTROL CODES (performed afterbillable check) ANI WATCH (adjustments to bill) 001 Verify Billable;found in ANI Passed all billable checks; but ANI had WATCH - CLIENTsource all been adjusted previously at vendor's, Client's or Telco'srequest for your Client # 002 Verify Billable; ANI WATCH - Passed allbillable checks; but ANI had CLIENT source been adjusted previously atClient's Client request for your Client # 003 Verify Billable; ANIWATCH - Passed all billable checks; but ANI had CLIENT source beenadjusted previously at vendor's or Telco or Vendor Telco's request foryour Client # 004 Verify Billable; found in ANI Passed all billablechecks; ANI had WATCH - GLOBAL been adjusted previously at vendor's,Client's or Telco's request for all Client ids 005 Verify Billable;found in ANI Passed all billable checks; ANI had WATCH - PRODUCT beenadjusted previously at vendor's, Client's or Telco's request for sameproduct type ZIP VERIFICATION 010 Verify Billable; Unable to match ZIPPassed all billable checks; unable to invalid find this Zip code forthis NPA/NXX- 011 Verify Billable; ZIP does not match Passed allbillable checks; Zip code does not match this NPA/NXX 012 VerifyBillable; ZIP matches to same Passed all billable checks; Zip codeMetropolitan area matches to same Metropolitan area as NPA NXX. ADDRESSVERIFICATION Note: The result of an AVS check does not mean that thetransaction is declined. This information may be advice only. The systemmay compare the AVS data with billing information for the buyer and passthe results of the comparison to the merchant. 020 Verify Billable; BNAmatch not found Passed all billable checks; no BNA match found for ANI021 Verify Billable; Unable to verify BNA Passed all billable checks;unable to invalid verify BNA to ANI info sent 022 Verify Billable; withzip-Match, Passed all billable checks; BNA Zip plus4-Match, locale-Matchcode +4 & locale (street address) matches info sent for ANI, Name doesnot match 023 Verify Billable; with zip-Match, Passed all billablechecks; BNA Zip plus4-Match, NoMatch-locale code +4 matches info sentfor ANI but locale (street address) does not match 024 Verify Billable;zip-Match, NoMatch- Passed all billable checks; BNA Zip plus4,locale-Match code & locale (street address) matches info sent for ANIbut +4 does not match 025 Verify Billable; zip-Match, NoMatch- Passedall billable checks; BNA Zip plus4, NoMatch-locale code matches infosent for ANI but locale (street address) & +4 does not match 026 VerifyBillable; NoMatch-zip, plus4- Passed all billable checks; BNA +4 andMatch, locale-Match locale (street address) matches info sent for ANIbut Zip does not match 027 Verify Billable; NoMatch-zip, plus4- Passedall billable checks; BNA +4 Match, NoMatch-locale matches info sent forANI but locale (street address) and Zip does not match 028 VerifyBillable; NoMatch-zip, Passed all billable checks; BNA localeNoMatch-plus4, locale-Match (street address) matches info sent for ANIbut ZIP and +4 does not match 029 Verify Billable; NoMatch-zip, Passedall billable checks; BNA does NoMatch-plus4, NoMatch- not match zip, +4or locale (street locale address) sent for ANI 030 Good Address & ZipMatch 031 Verify Address Match, Zip No Match 032 Verify Address Match,Zip Service Unavailable 033 Verify Address No Match, Zip Match 034Verify Address No Match, Zip No Match 035 Verify Address No Match, ZipService Unavailable 036 Verify Address Service Unavailable, Zip Match037 Verify Address Service Unavailable, Zip No Match 038 Verify AddressService Unavailable, Zip Service Unavailable AREA CODE CHANGE INDICATOR110 Update Indicates there has been an Code is sent in addition to thearea code change for this validation response codes. New phone NPA/NXXnumber is appended to record. Provided to update the account with thecorrect BTN. MISCELLANEOUS 120 Verify BTN and ANI do not match For usewhere BTN and ANI are passed and do not match. 121 Verify BTN or ANI aremissing from For use where BTN and ANI is missing record from recordUNBILLABLE CODES OFFNET 130 Unbillable NPA/NXX found in OFFNET - Areacode/exchange (NPA/NXX) GLOBAL combination resides in OFFNET DB. OFFNETis a territory where the LEC (Local Exchange Carrier) is unable toprovide 3rd party presentation in to its envelope. 131 UnbillableNPA/NXX found in OFFNET - Area code/exchange (NPA/NXX) CLIENT SPECIFICcombination resides in OFFNET DB specific for this Client id. 132Unbillable NPA/NXX found in OFFNET - Area code/exchange (NPA/NXX)PRODUCT combination resides in OFFNET DB specific for this product type.133 Unbillable NPA/NXX NOT VALID Area code/exchange is not a valid areacode exchange CLEC (CLECs are unable to provide 3rd party billpresentation in their envelopes.) 140 Unbillable Line number (NPA/NXX-BTN has been ported to a CLEC XXX) in CLEC Territory (competitive localexchange carrier). 141 Unbillable NPA/NXX not ON NET BTN has been portedto a CLEC (competitive local exchange carrier) and is not billable. 142Unbillable Line number OCN in CLEC Operating Company number for this OCNtable BTN was found on CLEC OCN table. The number is not billable. 143Unbillable Line number RAO in CLEC Regional Accounting Office number RAOtable for this BTN was found on CLEC RAO table. This BTN is notbillable. 42 BLOCK (4250s Only) 150 Unbillable Line Number has a blockfor Consumer has requested a block for all 4250 records MRCs (monthlyrecurring charges) from being billed to this phone number. BLOCK &CANCEL 160 Unbillable GLOBAL - Line number has Consumer requested blockto stop all been blocked to stop all charges from being billed to thischarges. number. 161 Unbillable CLIENT - Line number has a Consumerrequested a block to stop block to stop all charges from charges frombeing billed or to cancel this Client id. service for this phone numberfrom this Client id. UNBILLS 170 Unbillable Line number is Unbillable.Line number has been returned from the Local Telephone companies withinthe last 6 months as unable to be billed. LIDB FAILURE 180 UnbillableLine number failed LIDB Line Number has been returned from check -GENERAL LIDB as unbillable. 181 Unbillable Vacant NPA NXX No workingline #s in NPA NXX 182 Unbillable No Incoming Calls Line # cannot acceptincoming calls 183 Unbillable Denied ANI Auto decline of all attemptsfrom this ANI 184 Unbillable Calling Card block Auto decline of CallingCard number 185 Unbillable Collect Call Block Auto decline of Collectcalls to this number 186 Unbillable Third Party Call Block Auto declineall Third Party billed calls to this number 187 Unbillable Credit CardBlock Auto decline of charges billed to Credit Card 188 Unbillable GroupNumber Block Auto decline of attempts from this group. 189 UnbillableAudiotext Bock Number does not allow audiotext calls. 190 UnbillableExcessive Calling Card PIN Threshold for calling card attempts has hitsbeen exceeded. 191 Unbillable Line Number Block Auto decline of allcharges to this number 200 Unbillable Excessive Use - BTN BTN hasexceeded threshold 201 Unbillable Excessive Use DN DN has exceededthreshold 202 Unbillable Excessive Use - ANI ANI has exceeded threshold203 Unbillable Excessive USE - Calling Card Calling Card Pin hasexceeded Pin threshold 220 Unbillable Feature Group A Local telephoneswitch is Feature Group A 221 Unbillable PBX line Line # is a PBX line222 Unbillable WATS line Line # is a WATS line 223 UnbillableHotel/Motel Auto Quote w/ tax Hotel/Motel Auto Quote w/ tax 224Unbillable Hotel/Motel Auto quote w/o Hotel/Motel Auto quote w/o tax tax225 Unbillable Dormitory line Line # belongs to a dorm 226 UnbillableHospital line Line number belongs to a hospital 227 Unbillable Centrexline Line number belongs to CENTREX 228 Unbillable Alternate ServiceProvider Line # belongs to an alternate service provider 229 UnbillablePOTS line (collect or third Line # is plain old telephone service partycalls) lines for business or residential 230 Unbillable Pager # Linenumber belongs to pager 231 Unbillable PCS/Mobile/Cellular # Line numberbelongs to a wireless provider 240 Unbillable Line was disconnected w/oLine # was disconnected w/o a referral referral number 241 UnbillableLine Number changing Line is not connected yet. 242 Unbillable not used243 Unbillable DISCO w/o referral Line number has been removed fromservice w/o referral 244 Unbillable Temp DISCO Line number has beenremoved from service temporarily 245 Unbillable DISCO with referral Linenumber has been disconnected w/ referral or Operator takes calls 246Unbillable Temp DISCO w/ referral Line number has been removed fromservice temporarily w/ referral 250 Unbillable POTS line rating on rateplan POTS line is on a rate plan for business or residential messagerate 1 or 2 or flat rate 300 Unbillable Public - Incompatible interfacePublic phone with incompatible interface 301 Unbillable LEC PublicStandard PreP OT LEC Public phone standard interface; prepay overtime302 Unbillable LEC Public Alternate LEC Public phone alternateinterface; functions controlled by set 303 Unbillable LEC PublicStandard PP OT LEC Public phone standard interface; postpay overtime 304Unbillable IC Public IC Public Phone - Alternate Interface 305Unbillable IC Public Standard IC Public Phone - Standard Interface 306Unbillable LEC Public Special - PP OT LEC Public Phone- Special billingpost paid OT 307 Unbillable LEC Public Special - PreP OT LEC PublicPhone - Special Billing; Pre pay OT 308 Unbillable LEC Semi Public LECSemi Public Phone 309 Unbillable LEC Semi Public Phone (no LEC SemiPublic Phone does not allow collect or 3rd Party calls) collect or 3rdparty calls to this number 310 Unbillable LEC Prepaid Card LEC PrepaidCard Telecommunications station 311 Unbillable IPP (fka COCOT) StandardPayphone Standard interface 312 Unbillable IPP (fka COCOT) AlternatePayphone - Alternate interface 313 Unbillable Coinless (non IPP fkaCoinless Pay phone COCOT) 314 Unbillable Coinless (IPP fka COCOT)Coinless payphone 315 Unbillable Prison (non IPP fka COCOT) Prisonpayphone 316 Unbillable Prison (IPP fka COCOT) Prison Payphone 450Unbillable BNS: Voice Quote - without Charge quotes without tax tax 451Unbillable BNS: Voice Quote - with tax Charge quotes with tax CREDITCARD RESPONSE CODES 000 Approved Credit card approved 501 Decline/ErrorUser authentication Failed 502 Decline/Error Invalid tender Yourmerchant bank account does not support the following credit card typethat was submitted 503 Decline/Error Invalid transaction typeTransaction type is not appropriate for this transaction. For example,you cannot credit an authorization-only transaction. 504 Decline/ErrorInvalid amount 505 Decline/Error Invalid merchant information Processordoes not recognize your merchant account information. Contact your bankaccount acquirer to resolve this problem. 512 Decline/Error DeclinedPlease check the credit card number and transaction information to makesure they were entered correctly. If this does not resolve the problem,have the customer call the credit card issuer to resolve. 513Decline/Error Referral Transaction was declined but could be approvedwith a verbal authorization from the bank that issued the card. Submit amanual Voice Authorization transaction and enter the verbal auth code519 Decline/Error Original transaction ID not The transaction ID youentered for this found transaction is not valid. 520 Decline/ErrorCannot find the customer reference number 522 Decline/Error Invalid ABAnumber 523 Decline/Error Invalid account number Please check credit cardnumber and re-submit. 530 Decline/Error Account Lookup informationAccount provided found in system, Mismatch however, unique key provideddoes not match unique key in system. 531 Decline/Error Account does notexist Account provided not found in system 542 Decline/Error Invalidexpiration date Please check and re-submit 525 Decline/Error Transactiontype not mapped to this host 526 Decline/Error Invalid vendor account527 Decline/Error Insufficient partner permissions 528 Decline/ErrorInsufficient user permissions 550 Decline/Error Insufficient fundsavailable 551 Decline/Error Invalid transaction returned from host 552Decline/Error Processor not available 553 Decline/Error Credit errorPlease make sure you have not already credited this transaction, or thatthis transaction ID is for a creditable transaction. (For example, youcannot credit an authorization.) 554 Decline/Error Void error Pleasemake sure the transaction ID entered has not already been voided. Ifnot, then look at the Transaction Detail screen for this transaction tosee if it has settled. (The Batch field will be set to a number greaterthan zero if the transaction has been settled). If the transaction hasalready settled, your only recourse is a reversal (credit a payment orsubmit a payment for a credit). 555 Decline/Error Capture error Onlyauthorization transactions can be captured 556 Decline/Error Failed AVScheck Address and Zip code do not match 557 Decline/Error Cannot exceedsales cap For ACH transactions only 558 Decline/Error CVV2 Mismatch 800Unbillable LNP Only Look-Up, number LNP Only Look-Up, number was wasfound found in the LNP GTT database as ported. 801 Unbillable LNP OnlyLook-Up, number LNP Only Look-Up, number was not was not found found inthe LNP GTT database, not ported. 802 Unbillable LNP Only Look-Up, theLNP Only Look-Up, the NPNXX is not NPA/NXX is not a portable a portablerange. range. SYSTEM DOWN 994 Resubmit Message Format Error Messagereceived in invalid or unrecognized format. 995 Resubmit Time outSession timed out. 996 Resubmit Connection Failure Unable to connect.997 Resubmit Subsystem Failure Subsystem, such as LIDB, Credit Card,etc, not available. 998 Resubmit Network Failure Network Not Available999 Resubmit System Down System Unavailable

As mentioned above, the system 10 may translate the LIDB codes intomodified verification codes as shown in Table 2. These modified validitycodes are then mapped or translated. Table 3 below provides a list ofthe modified validity codes which are generated following the mappingcarried out by the processor module 54 to translate LIDB codes to themodified verification codes set out in Table 1. TABLE 3 LIDB/LNP SOURCETRANSLATIONS for ISP: Resp. Resp. Type Code LIDB rtfc Code In In ACTIONADMIN? Description type Out APP 000 Approved Calling card has anUnrestricted PIN. G1 000 APP 001 Approved Calling card has a RestrictedPIN. The g1 000 switch must verify that the DNI matches the first 10digits of the calling card before placing the call. APP 004 ApprovedCollect call - No verification is required. G1 000 APP 005 ApprovedThird-party call - No verification is G1 000 required. APP 006 ApprovedThere is a system error. S 999 APP 008 Approved Communications LinkTests “Good.” S 999 APP 010 Approved Commercial credit card is approvedand G1 000 the zip code matches, if the zip code was sent. APP 011Approved Y Bill-to number has an Admin. Override G1 000 to automaticallyapprove the transaction. (Admin. Reply) APP 012 Approved Originatingnumber (ANI) has an G1 000 Admin. Override to automatically approve thetransaction. (Admin. Reply) APP 013 Approved Dialed number (DNI) has anAdmin G1 000 Override to automatically approve the transaction. (Admin.Reply) APP 014 Approved Group number has an Admin. Override G1 000 toautomatically approve the transaction. (Admin. Reply) APP 015 ApprovedCommercial credit card is approved but CC 500 the zip code check isunavailable. APP 016 Approved Commercial credit card is approved but CC501 the zip code check is unavailable. Retry later. APP 017 ApprovedCommercial credit card is approved but CC 502 the zip code check is notsupported. APP 018 Approved Commercial credit card is approved and CC503 the address matches but the zip code does not match. APP 019Approved Commercial credit card is approved and CC 504 the address andthe zip code match. APP 020 Success LNP Only Look-Up, number was foundLNP 800 in the LNP GTT database as ported. APP 021 Success LNP OnlyLook-Up, number was not LNP 801 found in the LNP GTT database, notported. CON 050 Verify Collect call number has no block. o1 000 Verifyacceptance of the charge. CON 051 Verify Third-party call number has noblock. O1 000 Verify acceptance of the charge. CON 053 Denied Unable toauthorize, Automatic Code S 999 Gapping is in effect at the LIDB. Everythird query is dropped by the LIDB. CON 054 Denied Y Excessive Use - Thebill-to number G3 000 exceeded the high limit threshold in the Admin.fraud control system. (Admin. Reply) CON 055 Denied Y Excessive Bad PINAttempts - The O2 000 threshold for bad PIN attempts for the callingcard was exceeded in the Admin. fraud control system. (Admin. Reply)This is the same as reply code 309. CON 060 Conditional Y Low LimitWarning - The bill-to G3 000 number exceeded the low limit threshold inthe Admin. fraud control system. (Admin. Reply) CON 061 Conditional YLow Limit Warning - The dialed G3 000 number exceeded the low limitthreshold in the Admin. fraud control system. (Admin. Reply) CON 062Denied Y Excessive Use Dialed - The dialed G3 000 number exceeded thehigh limit threshold in the Admin. fraud control system. (Admin. Reply)CON 063 Conditional Y No Host Still Billable - There is no G2 180 LIDBcheck available, but the Customer has a billing agreement with this LEC.(Admin. Reply) CON 064 Approved Y Commercial credit card is approved butCC 505 the zip code and the address do not match. CON 065 Conditional YLow Limit Warning - The ANI G3 000 exceeded the low limit threshold inthe Admin. fraud control system. (Admin. Reply) CON 066 Denied YExcessive Use ANI - The ANI exceeded G3 000 the high threshold in theAdmin. fraud control system. (Admin. Reply) CON 070 Approved Callingcard has no service denial in the G1 000 Card Service Denial Indicatorfield. Calling card calls may be billed to this card number. CON 071Approved Calling card has no service denial in the G1 000 Pin ServiceDenial Indicator field. Calling card calls may be billed to this cardnumber. CON 080 Verify Collect calls - Accept intralata, Reject O1 000interlata collect calls. Recommend verify acceptance of the charge. CON081 Verify Third-party calls - Accept intralata, O1 000 reject interlatathird-party calls. Recommend verify acceptance of the charge. CON 082Verify Collect calls - Accept intralata, verify O1 000 interlata collectcalls. Recommend verify acceptance of the charge. CON 083 VerifyThird-party calls - Verify intralata, O1 000 reject interlatathird-party calls. Recommend Verify acceptance of the charge. CON 084Verify Collect call - Verify acceptance of the O1 000 charge by anOperator. CON 085 Verify Third-party call - Verify acceptance of O1 000the charge by an Operator. CON 086 Verify Collect call - Acceptintralata charge, O1 000 verify interlata charge with Operator. CON 087Verify Third-party calls - Verify intralata O1 000 charge with operator,reject interlata charge with Operator. CON 088 Verify Collect Calls:POTS Line G5 000 (Business/Residential) CON 089 Verify Third-PartyCalls: POTS Line G5 000 (Business/Residential) CON 090 Verify BNS:Centrex Line, Collect calls - Some G4 000 LECs allow billing to thistype of line, others do not. Verify Acceptance. CON 091 Verify BNS: POTSLine - Residential - G9 000 Message rate 1 CON 092 Verify BNS: POTSLine - Residential - G9 000 Message rate 2 CON 093 Verify BNS: POTSLine - Business - flat rate G9 000 CON 094 Verify BNS: POTs Line -Business - message G9 000 rate 1 CON 095 Verify BNS: POTS Line -Business - message G9 000 rate 2 CON 096 Verify BNS: POTS Line -Residential - flat rate G9 000 DENY 100 Denied Message Format ErrorMessage S 994 DENY 100 Denied Message Format Error- Date format S 994DENY 100 Denied Message Format Error-Header Message S 994 Error DENY 100Denied Message Format Error- Merchant ID S 994 Error DENY 100 DeniedMessage Format Error-No End of S 994 Header Indicator DENY 100 DeniedMessage Format Error-Header Data S 994 Indicator, did not contain datain each field of the message That was represented by the message textmap field DENY 100 Denied Message Format Error-PIN not numeric S 994DENY 100 Denied Message Format Error-Terminating S 994 Error (commercialcredit card only DENY 100 Denied Message Format Error-Terminating S 994Number not numeric DENY 100 Denied Message Format Error-Originating S994 Number not Numeric DENY 100 Denied Message Format Error-ChargeNumber S 994 not Numeric DENY 100 Denied Message Format Error-No EndHeader S 994 Indicator DENY 101 Denied Message Format Error Invalid S994 Customer/Terminal ID Number DENY 102 Denied Message Format ErrorInvalid Message S 994 Type DENY 103 Denied Message Format Error InvalidS 994 Transaction Type DENY 104 Denied Message Format Error InvalidSequence S 994 Number DENY 105 Denied Message Format Error Invalid DataS 994 Indicator DENY 105 Denied Message Format Error- Header Data S 994Indicator DENY 107 Denied Bad PIN format. PINs must be equal to S 994 orhigher than 2000. DENY 200 Denied Calling card blocked, missing customerS 994 record - There is no record of that calling card number in thedatabase. DENY 201 Denied BNS, missing customer record - There is S 994no record of that line number in the database. DENY 202 Denied MissingBNG - There is no record of S 994 that NPANXX in the database. DENY 203Denied Non-billable NXX - DPC table failure. G2 180 The NPANXX does nothave routing or allow billing, e.g. cellular. (LIDB or Admin. Reply)DENY 204 Denied Calling card blocked, screened data - A O2 000 screeningmechanism is in place at the LIDB that does not allow charges to thiscalling card. DENY 205 Denied Protocol converter problem - There is a S999 problem with the SS7 protocol converter. DENY 206 Denied BNS & NoCalling Card Calls - No o2 180 Host, Nonparticipating Group. This NPANXXexists but there is no LIDB host. (LIDB or Admin. Reply) DENY 207 DeniedLIDB Access Denied because no queries S 999 should be sent to this LIDBdestination. (Admin. Reply) DENY 208 Denied Calling card blocked,Screened Data on O2 000 PIN (Pin Service Denial Indicator) - A screeningmechanism is in place at the LIDB that does not allow charges to thisPIN. DENY 209 Denied External SS7 Problem - There is a S 999 formatproblem in the SS7 network DENY 210 Denied Calling card blocked,screened data - A O2 000 screening mechanism is in place at the LIDBthat does not allow charges to this calling card. DENY 211 DeniedCalling card is blocked because it has a O2 000 bad PIN or the PIN doesnot match database information. DENY 211 Denied Unexpected Data Value,Calling card O2 000 blocked, Bad PIN - This means a bad PIN was used orthere is no PIN on file. DENY 212 Denied Calling card blocked, PINExcessive G3 000 Use at LIDB Owner. - The PIN exceeded the highthreshold in the LIDB fraud control system DENY 213 Denied Vacant BNG -There are no working G2 181 lines in the NPANXX. DENY 214 Denied NoCollect calls - Collect calls are not O2 000 allowed to this linenumber. DENY 215 Denied No Third-party calls - Third-party calls O2 000are not allowed to this line number DENY 216 Denied BNS: LEC Public -Standard Interface G10 303 (functions controlled by the network) -Postpay Overtime DENY 217 Denied BNS: Coinless (non IPP fka COCOT) G10313 DENY 218 Denied BNS: semi-public phone - No Collect or G10 309Third-party calls are allowed to this line number. DENY 219 DeniedSpare - This LIDB response is not in use AV 180 at this time. DENY 220Denied Time-out, No response from Host - A S 180 response was notreceived from the host database within 4 seconds for a Telco query or 12seconds for a Bank card query. (LIDB or Admin. Reply) DENY 221 DeniedBNS Data unavailable, Error Message, S 180 No Host - No collect orthird-party calls should be allowed to this line number. DENY 222 DeniedCalling card Data unavailable, Error S 180 Message, No Host - No callingcard calls should be allowed to this line number. DENY 223 Denied BNS &Calling card, screened response O2 000 LIDB - A screening mechanism isin place at the LIDB that does not allow charges to this account number.DENY 224 Denied LIDB Misroute - The query was routed S 999 to the wrongLIDB. DENY 225 Denied Reject, Reroute - The LIDB could not S 994 readthe format of the query. DENY 226 Denied Unexpected Component - The LIDBS 994 cannot interpret the format of the query. DENY 227 Denied UDTS,SS7 Network problem - There is S 999 an SS7 network problem. DENY 228Denied BNS: Personal Communication Service G8 231 (PCS) DENY 229 DeniedBNS: Mobile G8 231 DENY 230 Denied Not Billable - The Customer does notG2 180 have a billing arrangement with the LEC for this NPANXX (OCNOn-Net Screening). DENY 231 Denied BNS: LEC Prepaid TelecommunicationsG10 310 Card Station DENY 232 Denied Feature Group A (FGA) G4 000 DENY233 Denied BNS: LEC Public - Alternate Interface G10 302 (functionscontrolled by set) DENY 234 Denied BNS: LEC Public - Special Billing -G10 306 Postpay Overtime (functions controlled by the network) DENY 235Denied BNS: LEC Public - Special Billing - G10 307 Prepay Overtime(functions controlled by the network) DENY 236 Denied BNS: Public -Incompatible Network G10 300 Interface (interface other than standard oralternate) DENY 237 Denied BNS: IC Public - Alternate Interface G10 304DENY 238 Denied BNS: IPP (fka COCOT) - Standard 311 Interface DENY 239Denied BNS: Pager G8 230 DENY 241 Denied General, Reject - The LIDBcould not S 994 read the format of the query. DENY 242 Denied Invoke,Reject - The LIDB could not S 994 read the format of the query. DENY 243Denied Return Result, Reject - The LIDB could S 994 not read the formatof the query. DENY 244 Denied Return Error, Reject - The LIDB could S994 not read the format of the query. DENY 245 Denied TransactionPortion, Reject - The LIDB S 994 could not read the format of the query.DENY 246 Denied BNS: Vacant Number - There is no line G2 180 numberassigned. DENY 247 Denied BNS: Disconnected without referral - G6 240The line number was disconnected with no referral to a new line number.DENY 248 Denied BNS: Changed to non-published number - o5 000 The linenumber was changed to a non-published number. DENY 250 Denied No CollectCalls, Screened Data - A O2 000 screening mechanism is in place at theLIDB that does not allow charges to this line number. DENY 251 Denied NoThird-party calls, Screened Data - A O2 000 screening mechanism is inplace at the LIDB that does not allow charges to this line number. DENY252 Denied BNS: Screened Data - A screening G7 191 mechanism is in placeat the LIDB that does not allow charges to this line number. DENY 253Denied BNS: Screened Data - A screening G7 191 mechanism is in place atthe LIDB that does not allow charges to this line number. DENY 254Denied BNS & No Calling Card, Unavailable O2 411 network resource - Thisline or card number is not in the database. DENY 255 Denied BNS:Screened Data - A screening G7 191 mechanism is in place at the LIDBthat does not allow charges to this line number. DENY 256 Denied BNS:Being changed - The line number G6 241 is being changed; it may not yetbe connected. DENY 257 Denied BNS: May not yet be connected - The G6 243line number may be new; it may not yet be connected. DENY 258 DeniedBNS: Temporarily disconnected - The G6 244 line number is temporarilydisconnected. DENY 259 Denied BNS: Disconnected, calls being taken G6245 by operator - The line number is temporarily disconnected, theoperator is taking calls. DENY 260 Denied BNS: Temporarily removed fromG6 244 service - The line number is temporally removed from service.DENY 261 Denied BNS: Not in service for incoming calls - G2 182 Thisline number cannot accept incoming calls. DENY 262 Denied BNS:Temporarily disconnected at G6 245 customer request without referral -The line number is temporarily disconnected at the request of thecustomer without referral. DENY 263 Denied BNS: Temporarily disconnectedat G6 246 customer request with referral - The line number istemporarily disconnected at the request of the customer with referral.DENY 264 Denied BNS: Changed with referral to new o5 000 number - Theline number was changed. A referral to another line number is in place.DENY 265 Denied Calling card blocked, PIN Nonpayment - O2 000 Thecalling card is blocked because of nonpayment. DENY 266 Denied Callingcard blocked, Service O2 000 Restriction on PIN - There is a servicerestriction on this PIN. DENY 267 Denied Calling card blocked, no PINsassigned. O2 000 There is no PIN assigned to this calling card/linenumber. DENY 268 Denied Calling card blocked, service denial - O2 000There is a service restriction on this calling card. DENY 269 DeniedCalling Card - The calling card is a O2 000 CIID (proprietary card) forwhich there is no host. DENY 270 Denied BNS: Unexpected Data Value - NoS 994 Collect or Third-Party Calls are allowed. DENY 272 Denied LIDB/CCCResponse Time-out - A S 180 response was not received from the hostdatabase within 4 seconds for a Telco query and 12 seconds for a Bankquery. DENY 273 Denied No Collect Calls at Customer Request - O2 000 Theend user customer requested the block for collect calls to this linenumber. DENY 274 Denied BNS & No Calling Card Calls: Screened O2 000data. DENY 275 Denied BNS: Hotel/Motel Auto Quote - with G4 000 tax DENY276 Denied BNS: Dormitory Line G4 225 DENY 277 Denied BNS: Hotel/MotelAuto Quote - without G4 000 tax DENY 278 Denied BNS: PBX Line G4 221DENY 279 Denied BNS: Prison (IPP fka COCOT) G10 316 DENY 280 Denied BNS:WATS Line G4 222 DENY 281 Denied No Third-party calls at Customer O2 000Request - The end user customer requested the block for third-partycalls to this line number. DENY 282 Denied BNS: LEC Public - Standardinterface - G10 301 Prepay Overtime DENY 283 Denied BNS: Coinless (IPPfka COCOT) G10 314 DENY 284 Denied BNS: IC Public - Standard InterfaceG10 305 DENY 285 Denied BNS: Voice Quote - without tax o6 450 DENY 286Denied BNS: Voice Quote - with tax o6 451 DENY 287 Denied BNS: IPP (fkaCOCOT) - Alternate G10 312 Interface DENY 288 Denied BNS: Hospital G4226 DENY 289 Denied BNS: Prison (non-IPP fka COCOT) G10 315 DENY 290Denied BNS: LEC Semi-Public G10 308 DENY 291 Denied BNS: SubsystemCongestion S 180 DENY 292 Denied BNS: Subsystem Failure S 180 DENY 293Denied BNS: No translation for address of such S 180 nature DENY 294Denied BNS: Unequipped User S 999 DENY 295 Denied BNS: Network Failure S180 DENY 296 Denied BNS: Network congestion S 999 DENY 297 Denied BNS:Cellular (cellular is distinct from G8 231 mobile) DENY 298 Denied BNSand Calling Card - Although the G4 228 NPANXX belongs to SWBT the end-user account number is no longer is a SWBT customer. The line number nowbelongs to another local service provider. DENY 299 Failure LNP OnlyLook-Up, the NPANXX is LNP 000 not a portable range. DENY 301 Denied YDenied Originating Number (ANI) - The G2 183 ANI has an Admin. block toautomatically decline all attempts from this line number. (Admin. Reply)DENY 302 Denied Y Terminating Number (DNI) has an G2 182 Admin. block toautomatically decline all attempts to this line number. (Admin. Reply)DENY 303 Denied Y Calling card has an Admin. block to G2 000automatically decline all attempts to this line number. (Admin. Reply)DENY 304 Denied Y Collect Number has an Admin. block to G2 000automatically decline all attempts to this line number. (Admin. Reply)DENY 305 Denied Y Third Party Number has an Admin. G2 000 block toautomatically decline all attempts to this line number. (Admin. Reply)DENY 306 Denied Y Commercial credit card has an Admin. G2 000 block toautomatically decline all attempts to this line number. (Admin. Reply)DENY 307 Denied Y Group Number has an Admin. block to G2 000automatically decline all attempts from this group. (Admin. Reply) DENY308 Denied Y Global Negative Database Block - There G2 000 is an Admin.block in the Global Negative Database to this line number for theAudiotext Industry. (Admin. Reply) DENY 309 Denied Y Excessive callingcard PIN hits - The G2 000 threshold for bad PIN attempts for a callingcard was exceeded in the Admin. fraud control system (Admin. Reply).This is the same as reply code 055. DENY 400 Denied Commercial creditcard, Invalid 506 Commercial credit card - This is not a validcommercial credit card account number. It failed the MOD 10 check. Alsoan invalid amount, invalid date or a format error may cause thisresponse. (Host or Admin. Reply) DENY 401 Denied Commercial credit card,Call issuer - 507 The authorization attempt triggered a flag in thefraud control system of the issuing bank, Banknet or VISAnet. DENY 402Denied Commercial credit card, Confiscate card - 508 No billing isallowed to this account number. If possible confiscate this card. DENY403 Denied Commercial credit card, Authorization 509 Declined - Nobilling is allowed to this account number. DENY 404 Denied Commercialcredit card, Unable to 510 Validate Account Number - There is problem inauthorizing this account number. DENY 405 Denied Commercial credit card,Card expired - 511 No billing is allowed to this account number becausethe card has expired DENY 406 Denied Commercial credit card - Invalid512 Merchant ID DENY 408 Denied Commercial credit card, Invalid card 513and Address (zip code) - Both the account number and the address or zipcode are invalid. Do not allow billing to this account number. DENY 409Denied Commercial credit card, System 514 Problem - There is a technicalproblem with the authorization system of the issuing bank, Banknet orVISAnet. DENY 420 Denied Commercial credit card, Over 515 withdrawallimit - This account has exceeded the withdrawal threshold in theauthorization system of the issuing bank DENY 421 Denied Commercialcredit card, Over credit 516 limit - This account has exceeded thecredit threshold in the authorization system of the issuing bank DENY422 Denied Commercial credit card, Lost card, 517 Confiscate - Thisaccount number was reported lost. No billing is allowed to this accountnumber. If possible confiscate this card. DENY 423 Denied Commercialcredit card, Stolen card, 518 Confiscate card - This card was reportedstolen. No billing is allowed to this account number. If possibleconfiscate this card. DENY 424 Denied Commercial credit card, InvalidPin - 519 This means a bad PIN was used. DENY 425 Denied Commercialcredit card, Allowable 520 Number of PIN Tries Exceeded - The thresholdfor bad PIN attempts for a calling card was exceeded in theauthorization system of the issuing bank, Banknet or VISAnet. DENY 426Denied Duplicate transaction. The 521 Authorization host considers thisa duplicate transaction.

In the embodiment of the invention depicted in the drawings, regardlessof the type of service provider or the type of validation request,clients or vendors may need a profile so that the process or methodcarried out by the system 10 knows how to treat the request. The clientor vendor profile may be set up in a database, which includes theindicators that are set for the type and tests for each request, whichwill be subsequently received from the vendor.

The first table shows the operations in the BTN test descriptionsprocess. In one exemplary embodiment, a set of core tests is run foreach client. Additionally, clients may have some configuration optionsto identify the tests that best fit their program. BILLABLE BTN TESTsPROCESS TESTs PURPOSE VAL/Pre- Client profile Client profile for each idfor BTN validation process test bill flags. VAL only ANI = BTNDetermines if originating number = BTN input by caller. VAL/Pre- Invalid# Ids Invalid NPAs & NXXs bill OFFNET VAL/Pre- Global OFFNET Ids(NPA)NXX & OCN combinations where there is bill not a B&C agreementVAL/Pre- Product Ids (NPA)NXX & OCN combinations where the traffic billOFFNET type is not approved to bill (Jul. 24, 2001: MRC only for NECAand Illuminet Only) VAL/Pre- Client OFFNET Ids (NPA)NXX & OCNcombinations where there the bill Client id (7###) is not approved tobill VAL/Pre- Special Calling Ids (NPA)NXX & OCN combinations of specialcalling bill Card OFFNET card #s for non-calling card traffic that areunable to be billed VAL/Pre- Plan OFFNET Ids (NPA)NXX & OCN combinationswhere a Client bill Plan is not approved to bill VAL/Pre- ONNET Ids(NPA)NXX & OCN combinations where there are bill B&C agreements VAL/Pre-CLEC Ids (NPA)NXX-xxxx's are not billable due to CLEC for bill allClients. VAL/Pre- 4250 BLOCK Ids (NPA)NXX-xxxx's that have a 4250billing block bill (for MRC only) VAL/Pre- UNBILL Ids (NPA)NXX-xxxx'sthat have unbilled previously for bill all Clients VAL/Pre- Block &Cancel - Ids (NPA)NXX-xxxx's that requested a Block and/or bill GLOBALCancel; usually institutional VAL/Pre- Block & Cancel - Ids(NPA)NXX-xxxx's that requested a Block and/or bill Client SpecificCancel for a particular Client id VAL/1^(st) + n Val Code Cache Ids(NPA)NXX-xxxx & Return Code combinations for Pre-bill previous requestVAL/1^(st) LIDB Validity To determine the billable status of the returncode from Pre-bill Test the LIDB dip VAL/1^(st) LIDB CLEC Ids RAOs thatbelong to CLECs Pre-bill RAO VAL/1^(st) LIDB CLEC Ids known CLEC OCNsPre-bill OCN VAL/1^(st) LIDB State To determine if the returned LIDBcode is a state Pre-bill Specific specific code and then a conversion tothe billable OCN Conversion for the ONNET check VAL/1^(st) LIDB ONNETIds billable (NPA)NXX & returned OCN combinations Pre-bill ALL VAL TransLog Log of each validation request and response by Client ID

BTN CREDIT SCORING PROCESS TESTs PURPOSE VAL/Pre- AREA CODE Provides thenew area code for the line number while bill Change indicator inpermissive dialing period. Val ZIP MATCH ZIP matches zip codes for (NPA)NXX (not in production as of June 2001) VAL/Pre- ANI WATCH -(NPA)NXX-xxxx's where there a refund/chargeback bill CLIENT has beenissued previously for this Client ID (SOURCE: all) VAL/Pre- ANI WATCH -(NPA)NXX-xxxx's where there a refund has been bill CLIENT issuedpreviously for this Client ID (SOURCE: client) VAL/Pre- ANI WATCH -(NPA)NXX-xxxx's where there a chargeback/bad bill CLIENT debt has beenissued previously for this Client ID (SOURCE: ebi/telco) VAL/Pre- ANIWATCH - (NPA)NXX-xxxx's where there a bill GLOBAL refund/chargeback/baddebt has been issued (SOURCE: all) previously from CLIENT, ebi or telcoVAL/Pre- ANI WATCH - (NPA)NXX-xxxx's where there a bill PRODUCTrefund/chargeback/bad debt has been issued (SOURCE: all) previously forthe same product VAL Address Not Available Verification

TEST BEFORE FIRST BTN BILLING PROCESS TESTs PURPOSE VAL/Pre- LEC CAREDetermines if the ILEC bill FEED owns the Acct. for billing VAL/Pre- Bizvs Res Determines the commercial or bill consumer status for creditscore

Example TESTs PROCESS TESTs PURPOSE VAL/Pre- Threshold by Determineswhether the BTN has bill Client met a Client specific threshold VAL/Pre-LEC PROV feed To determine if LEC owns Acct bill VAL/Pre- Credit CheckCredit header files check from Credit bill source VAL/Pre- New within 90Determines if BTN is less than bill days 90 days old; affects creditscoreON/OFFNET Family Tables (Billing Coverage)

The OFFNET table family contains OCN & NPA_NXX combinations wherebilling is not approved. If found, the BTN does not continue on thevalidation path.

The ONNET table determines if an NPA_NXX & OCN combination can be foundamong the billable combinations. In this case a match allows the BTN tomove further on the validation path. A no match will return a failure.

The CLEC table consists of CLECs that the proprietor, or user of thesystem 10, does not have billing contracts with. This table is specificto the line number. Sources dictate the fields that will be present forthe record. A match here is considered a fail and does not continue.

The 4250 Block table consists of specific line numbers that cannot bebilled for 4250-01 record types. A match in this table stops thevalidation movement.

Bill Control Family Tables

The Unbills or unbillable table holds all the BTNs that have been sentto a subscribers' bill page but could not be placed on the bill page forvarious reasons. A match here halts the validation sequence for thesubject BTN.

Block and cancel tables identify BTNs that have requested a permanent ora Client specific block for billing. A match sends a failed response.

Validation Cache is a table that holds responses in order not to processduplicates (e.g. Submit pressed 10 times). A match here will return thecode stored from a previous request.

LIDB Family Tables

LIDB is a third party that supplies information to the phone line numberlevel. The goal is to test and store as many relevant fields as can berequested in a transaction.

The LIDB Validity Table translates the LIDB code into a billable ornon-billable response according to predefined business rules. A failhere will halt the validation for the request.

The State specific table is a conversion from a true OCN to a knownState Specific OCN that is billable. A match here will trigger theconversion, the BTN continues in the validation process.

The transaction log is the history of each transaction request andresponse that is processed through the validation system.

The TPM indicates that an NPA is in the permissive dialing period. Amatch here appends the record with the updated number for a recordupdate.

The ANI Watch has BTNs that have been given an adjustment for charges bythe Client, proprietor or user of the system 10 or the Telco. This is tohelp the client determine the credit score for the BTN.

Unlike the conventional use of the LIDB database that uses the LIDB datato obtain information on a destination/termination or recipient locationor subscriber unit, the system 10, in one exemplary embodiment, uses theindustry standard LIDB database to obtain relevant information on theinitiating subscriber line. The subscriber line reference data obtainedfrom the LIDB database is then processed to generate modified validitycodes, which provide a vendor with data to facilitate deciding whetheror not a transaction should be processed. The LIDB/LNP database may bequeried as if a collect call event is occurring and a call is thusmimicked. The processing of the transaction, in one exemplaryembodiment, involves communicating the relevant transaction data to afolder of the subscriber with a relevant Telco. The method of, andsystem 10 for, validating the billing account associated with thesubscriber line allows, for example, a subscriber line to be used tovalidate and conclude a transaction instead of using a conventionalpayment techniques such as a credit card, debit card, bank accountdetails or the like.

A current industry-wide problem is the lack of ability of a serviceprovider to identify when a line subscriber has switched his service toa CLEC since the service provider may not have an existing billingarrangement with such a CLEC and may also not have a source for the BNAto allow for a direct billing solution. LNP databases were originallyestablished for the purpose of directing call routing activities amongfacilities-based carriers and most telephone numbers ported to a CLEC donot involve a facility change (i.e. the CLEC is simply reselling theincumbent LEC's facilities). This means that, for billing decisionpurposes, LNP queries may provide an incorrect response.

In one embodiment of the present invention, the LNP queries have beenenhanced by analyzing and interpreting other field elements includedwithin the query response. Specifically, certain values or, in somecases, the absence of certain values, in the Operating Company Number(“OCN”) and/or the Regional Accounting Office (“RAO”) fields, allowsfurther accuracy in the validation response. While the definitions ofthe OCN and RAO field elements can be obtained from industry sources,their interpreted use in the validation process is unique to the presentinvention. Use of these additional data elements can improve thereliability of the validation event.

In addition, the present invention may include supplementing LNP resultswith CARE queries in LEC regions where LNP results are inadequate andCARE costs are not otherwise prohibitive based on the retail price ofthe underlying service. CARE may provide a reliable result onCLEC-ported numbers since its basic purpose is to provide subscriberaccount information (such as billing name and address). Once a number isported to a CLEC, the incumbent LEC no longer has subscriberresponsibility and will, therefore, return an “unavailable” response,even if the LEC's dial-tone facility is still being utilized. Thisnegative response is then used to generate a “deny” status on thesubscriber based on the current lack of CLEC billing support.

The exemplary embodiment of the present invention may supplement thevalidation process through the use of internal databases built frominformation gathered throughout the billing and collection process andprocess logic gleaned from previous billing experience.

It is important to appreciate that all of the operations in the methodexecuted by the system 10 need not be executed in real-time. In oneexemplary embodiment, after the approval code 000 has been generated bythe system 10 at operation 134, the system 10 terminates itspre-validation check routine as shown at operation 136. At this pointthe system 10 may merely provide pre-validation data or verificationdata to indicate to the vendor 12 whether or not the subscriber line isbillable. Thus the system 10 may, in a first interaction with the vendor12 provide pre-validation data, and in a second interaction processbilling information. During the processing of billing information thevalidation process may once again be executed. In certain embodiments,the first interaction may be in the form of a registration processduring which the validation procedure is carried out to register asubscriber line. The vendor may then conduct numerous transactions withsubscriber and subsequent validation checks on the subscriber line maythen only be carried out on a periodic basis.

After the validation code has been sent to the vendor 12, and thepre-validation procedure has been completed, the system 10 then carriesout the fraud checks on a non real-time basis (usually during the next48 to 72 hours) as shown in operations 140 to 144. The informationobtained during the fraud control check, if necessary, is used to updatethe various databases. In particular, after a BTN has been successfullyvalidated but before a billing event takes place, the CARE investigationoperations 140 to 144 may be executed. In the exemplary embodiment, thesystem 10 is arranged to interrogate off-site CARE databases and theresults of the enquiry are stored in the CARE database 46. Checks on thedata received from the CARE databases are then performed; whereafter oneor more of the other databases may be updated with the results. Forexample, the CARE database may be updated with new within 90 daysinformation, business indicator information, or the like. In theexemplary embodiment, CARE codes 2618 and 2619 indicate that the BNA isnot available and that the LEC no longer owns the account.

The updating of the databases following the CARE investigation may allowenhanced future checks by the system 10 in a subsequent pre-validationprocedure or subsequent registration validation event. The updatedinformation may be provided to the vendor 12. However, if the BTNinformation returned from the CARE database does not meet predefinedcriteria, the other databases of the system 10 may not be updated.

In the embodiment described above, information on the subscriber line 17is forwarded by the service provider or vendor 12 to the system 10 forvalidation. However, in other embodiments of the invention, the consumeror customer 11 may call the system 10 directly, as shown by line 150 inFIG. 5, and the ANI may then be obtained by the system 10 directly fromthe customer 11 and not indirectly from the vendor 12. Furthersubscriber line data, e.g. BTN, address of the customer 11 and so on,may then also be obtained directly from the customer 11. For example,the customer 11 may have appropriate software installed on his/her PCwhich allows the customer 11 to dial into the system 10 in an automatedfashion should he/she wish to charge any requested goods or services tohis/her subscriber account. The system 10 would then validate thesubscriber line number 17 using the method described above. The system10 then typically communicates a validation code (e.g. corresponding toapproval or non-approval) to the vendor 12 as shown by line 152. Thevendor 12 would then conclude the transaction with the customer 11 ifthe subscriber line has been validated.

The proprietor or user of the system 10 may function as a type ofclearing house. In particular, the proprietor or user of the system 10may be responsible or accountable for payment for the goods or servicesfor each transaction to the service provider or vendor 12 and, in turn,receive payment from the Telco 13. As mentioned above, the system 10 mayupdate the telephone bill or account of the subscriber in an automatedfashion (see line 154) and the account that the subscriber or customer11 receives (see FIG. 6 and line 156 in FIG. 5) includes the charges forthe goods and/or services provided by the vendor 12. The customer 11 maypay the Telco 13 (see line 155), the Telco 13 may pay the system 10 (seeline 156), and the system 10 may pay the vendor 12 (see line 160). It isimportant to appreciate that these payments need not take place at thesame time. In one exemplary embodiment, the payments between the Telcoand the system 10, and the system 10 and vendor 12, take placeperiodically in a batch fashion.

FIG. 7 shows a diagrammatic representation of machine in the exemplaryform of a computer system 600 within which a set of instructions, forcausing the machine to perform any one of the methodologies discussedabove, may be executed.

The computer system 600 includes a processor 602, a main memory 604 anda static memory 606, which communicate with each other via a bus 608.The computer system 600 may further include a video display unit 610(e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT)). Thecomputer system 600 also includes an alpha-numeric input device 612(e.g., a keyboard), a cursor control device 614 (e.g., a mouse), a diskdrive unit 616, a signal generation device 618 (e.g., a speaker) and anetwork interface device 620.

The disk drive unit 616 includes a machine-readable medium 622 on whichis stored a set of instructions (software) 624 embodying any one, orall, of the methodologies or functions described herein. The software624 is also shown to reside, completely or at least partially, withinthe main memory 604 and/or within the processor 602. The software 624may further be transmitted or received via the network interface device620. For the purposes of this specification, the term “machine-readablemedium” shall be taken to include any medium that is capable of storing,encoding or carrying a sequence of instructions for execution by themachine and that cause the machine to perform any one of themethodologies of the present invention. The term “machine-readablemedium” shall accordingly be taken to included, but not be limited to,solid-state memories, optical and magnetic disks, and carrier wavesignals.

Thus, a method and system to validate data associated with a subscriberline of a telecommunication network have been described. Although thepresent invention has been described with reference to specificexemplary embodiments, it will be evident that various modifications andchanges may be made to these embodiments without departing from thebroader spirit and scope of the invention. Accordingly, thespecification and drawings are to be regarded in an illustrative ratherthan a restrictive sense.

1. An identity verification method, the method comprising: obtainingautomatic number identification (ANI) data or billing telephone number(BTN) data associated with a subscriber line of a telecommunicationsnetwork; obtaining identification data associated with a subscriber,said identification data being different from the ANI data or the BTNdata; searching a first database using the ANI data or the BTN data todetermine first reference subscriber data; searching a second databaseusing the identification data to determine second reference subscriberdata; comparing the first reference subscriber data to the secondreference subscriber data; and verifying an identity of the subscriberbased on the comparing.
 2. The identity verification method of claim 1,wherein verifying the identity of the subscriber based on the comparingcomprises verifying if the first reference subscriber data correspondsto the second reference subscriber data.
 3. The identity verificationmethod of claim 1, wherein the obtaining of the ANI data or the BTNdata, and the identification data, comprises obtaining the ANI data orthe BTN data and the identification data from a merchant, the merchantbeing in the process of selling goods or services to the subscriber. 4.The identity verification method of claim 1, wherein the identificationdata is a ZIP code, and the second database is a ZIP data source.
 5. Theidentity verification method of claim 1, wherein the identification datais address data, and the second database is an address data source. 6.The identity verification method of claim 1, wherein the first databaseis a line identification database (LIDB), and the second database isdistinct from the first database.
 7. The identity verification method ofclaim 1, wherein the second reference subscriber data comprises anaddress of the subscriber.
 8. The identity verification method of claim1, wherein the comparing of the first reference subscriber data to thesecond reference subscriber data comprises determining whether a matchexists within a predefined range or geographic area.
 9. The identityverification method of claim 1, further comprising providing averification status notification to a merchant.
 10. The identityverification method of claim 3, further comprising, prior to thesearching, ascertaining if the ANI data or the BTN data corresponds to abillable subscriber line by performing at least one of: interrogating anetwork database with the ANI data to determine if the subscriber lineis a billable subscriber line, and, if so, generating a decline statusor an approved status in response to the interrogation; searching athreshold database to determine whether an account associated with thesubscriber line has reached a maximum monetary amount; searching an offnetwork (OFFNET) database to determine whether an industry standardNumbering Plan Area (NPA), an NXX, or an operating company number (OCN)of the subscriber line is present in the OFFNET database; searching anon network (ONNET) database to determine whether an industry standardNumbering Plan Area (NPA), an NXX, or an operating company number (OCN)of the subscriber line is present in the ONNET database; searching acompetitive local exchange carrier (CLEC) database to determine whetherthe ANI data or the BTN data is known to have ported to a CLEC andwhether transactions cannot be billed to an account associated with thesubscriber line; searching a 42 BLOCK database to determine whether abilling block has been imposed on the subscriber line; or searching ablock and cancel database to determine whether a request has been madeto prevent further transactions from being billed to an accountassociated with the subscriber line. searching an unbilled database todetermine whether there is a history of unbillable bills associated withthe subscriber line; and searching an unpaid bills database to determinewhether there is a history of unpaid bills associated with thesubscriber line.
 11. The identity verification method of claim 1,further comprising, after determining of the first reference subscriberdata, using the first reference subscriber data to search a regionalaccount office (RAO) database to determine whether the subscriber lineis billable.
 12. The identity verification method of claim 1, furthercomprising, after determining the first reference subscriber datareceiving an operating company number (OCN) from the first database;determining whether the OCN corresponds to a known competitive localexchange carrier (CLEC); and determining whether the OCN corresponds toan off network (OFFNET) CLEC.
 13. The identity verification method ofclaim 1, further comprising, after determining the first referencesubscriber data, using the first reference subscriber data to determineif a new Numbering Plan Area (NPA)/NXX and an operating company number(OCN) combination for the subscriber line are guidable to a correcttelephone company for billing.
 14. The identity verification method ofclaim 1, further comprising interrogating a customer account recordexchange (CARE) database.
 15. The identity verification method of claim1, further comprising interrogating an ANI watch database to determinewhether an account associated with the subscriber line has beenpreviously adjusted.
 16. An identity verification method, the methodcomprising: obtaining automatic number identification (ANI) data orbilling telephone number (BTN) data associated with a subscriber line ofa telecommunications network; obtaining identification data associatedwith a subscriber, where said identification data is different from theANI data or the BTN data; requesting a search of a first database usingthe ANI data or the BTN data to determine first reference subscriberdata; requesting a search of a second database using the identificationdata and the first reference subscriber data to determine secondreference subscriber data; and verifying an identity of a subscriberbased on the second subscriber data.
 17. An identity verification systemcomprising: a network interface device to receive: automatic numberidentification (ANI) data or billing telephone number (BTN) dataassociated with a subscriber line of a telecommunications network, andidentification data associated with a subscriber, said identificationdata being different from the ANI data or the BTN data; a processor toexecute instructions stored in memory, the instructions comprising:requesting a search of a first database using the ANI data or the BTNdata to determine first reference subscriber data, requesting a searchof a second database using the identification data and the firstreference subscriber data to determine second reference subscriber data,and verifying an identity of the subscriber based on the secondsubscriber data.
 18. The identity verification system of claim 16,wherein the first database and the second database are remotely locatedfrom the network interface device and the processor.
 19. The identityverification system of claim 16, wherein the processor is to execute theinstructions stored in memory in real-time.
 20. The identityverification system of claim 16, wherein the processor is to executeinstructions to search one or more remote databases comprising one ormore of a competitive local exchange carrier (CLEC) database, a 42 BLOCKdatabase, a Block and Cancel database, an unpaid bills database, an offnetwork database, an on network database, an address verificationdatabase, a regional account office (RAO) database, an operating companynumber (OCN) database, or a customer account record exchange (CARE)database.